@Mgrdich approve, please, if you haven't got questions more. My next task relates to this part of code with Brokers and I don't want a lot of conflicts.

It looks good, but SizeCell still has the any typing instead of a generic

@Mgrdich I have rollbacked SizeCell to unknown as you wish)))

Let's look at the errors related to the table (where the others in main came from - I don't know).
And I found an interesting peculiarity. Now in the table for the columns field there is a generic TValue, which breaks the typing and excludes the possibility of processing unions for the column value. You can notice this error in the BrokersList.tsx file . And it is not about undefined type. Even if you take the BrokersTableRow type of this kind for checking, TS will start complaining to you that Type number is not assignable to type string. Although this should not be the case.

Then why did you need a generic TValue in the Table component? Taking into account that it is not used anywhere in the code of the component itself, but only thrown into props. Moreover, if we look at the typing of the tanstack/react-table library itself, we will see that the developers of the library themselves have strictly typed the columns parameter to be passed to useReactTable. And there it is typed as columns: ColumnDef<TData, any>[]. That is, even the library creators themselves do not accept column value as a generic. And we can't do it even if we really wish we could.

Why this problem was not noticed earlier in other code places? Because in all places where table columns were formed, either an explicit generic was thrown into getValue, or unknown was thrown into CellContext instead of TValue.... That is, in fact, there was never a strict TValue typing.

My proposed scheme of table composition assumes strict typing of components used in the cell field, strict typing of the result returned by the getValue function (not at the place of use, but at the stage of table generation, automatically).To do this, we just need to remove the already unused generic TValue from the implementation of the NewTable component. What do you think?

i think i intercommunicated , i will take a look why the typescript is breaking in your branch.

we needed the generic to make the Table component full generic , so it can infer the correct types base on the table data.

No problem, please take a look. It is not necessary to use a generic TValue in ColumnDef in a table component. It is enough to strictly describe the columns at the stage of their creation, and the default tanstack table tools will correctly pick up the column types